Remove legacy XUnitWrapper test tree infrastructure#123110
Merged
jkoritzinsky merged 6 commits intodotnet:mainfrom Jan 30, 2026
Merged
Remove legacy XUnitWrapper test tree infrastructure#123110jkoritzinsky merged 6 commits intodotnet:mainfrom
jkoritzinsky merged 6 commits intodotnet:mainfrom
Conversation
…without going through an xunit harness.
…standalone runner
Contributor
|
Tagging subscribers to this area: @dotnet/runtime-infrastructure |
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
3 tasks
This was referenced Jan 15, 2026
steveisok
approved these changes
Jan 30, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Now that we've moved entirely to the new test system, we can remove the old XUnitWrapper logic from the test build system and the helix publishing. This will help us be able to further evolve the test system as we will now have a baseline of 1 test running mechanism instead of 2.
To ensure compatibility with some of the community's workflows, I've added a very basic local test runner for the BuildAllTestsAsStandalone=true scenario. This scenario used to fall back on the old test runner system. With that system gone, a replacement was needed.